Assigning Aliases

Whenever you make an assembly request to Document Generation Services you need to provide the Content Identifier. The Destination Value is the long version of the Content Identifier. In order to make that simpler you can create an Alias which allows you to use the first part of the Original Value instead of the entire Destination Value.

  • Original Value must end in “\.(.*)”
  • Destination Value is in the following format
    • Starts with “ expere://”
    • An integer value for the Account ID [period separator]
    • A string value for the name chosen when the library was deployed [period separator]
    • An integer value for the version of the library chosen during deployment [period separator]
    • A string value for the organization (AKA precedence) level to use from Organizations.xml which is part of the ZIP file used for the library. If the library only has one organization level defined, which is the case if you don’t have any custom content then this value will be “ORG.WoltersKluwerFinancialServices.Root”. If there are multiple organization levels defined then this value will be the name of the custom organization level you want to use.
    • Must end in “.$1.”
  • It is also possible to create an alias by going to the Manage Libraries tab, then choose the library to add an alias for, then choose Details and then choose the Add an Alias option.
    • If you add the alias this way the Original value already contains the “\.(.*)” at the end, however, it is simpler if you remove the “expere://” from the beginning.
    • The New Value needs to have the organization name added before the $1.
  • Another option available through the Add an Alias functionality is to add a Pre-Render Translation.
    • This allows you to create a stylesheet that will be applied to the transaction data before the documents are rendered. This could be useful for adding default data to a transaction or changing certain data, if desired.
  1. Select the name of the library.
  2. Click on Details.
  3. Click Add an Alias.
  4. Change the Account ID to the Account ID for which you are creating the alias.
  5. Modify the Original value to represent what the calling application value is when retrieving the content.
    Example: expere://(.*)
  6. Modify the Destination Value to represent the interpretation of the library utilized for the application.
    Example: expere://1.DocOneDefault.1.$1.
    Note: For DocOne Default always leave the Account number as 1. Ensure that the Version matches the version that was just deployed.
    Note: The value before the library name is the Account; the value after the library name is the version.
  7. Click the Pre-Render Translation browse button. This allows you to upload an XSL stylesheet to run against your transaction data.
    Note: This is an optional feature; users are not required to upload an XSL stylesheet.
  8. Select Add.